Autofocus Advance
Original Post
As promised in the recent thread "What system do you use right now?", here is my current system and favourite AF tweak. With apologies to Mark and the Nintendo company, I named it Autofocus Advance.
Rules
Each AF page is divided into two areas (such as by a dividing line about half way down the page, using two columns, or using facing pages.) The first is the new task area, the second is the reentered task area.
Rules for cycling through the pages, task selection, and dismissal are as in Autofocus 1. The two areas are treated as if they formed a single, contiguous page. Free space in the reentered task area doesn't keep from finishing or dismissing pages.
New tasks are entered in the new task area on the last page of the list. A new page is started when the last page's new task area is full.
Reentered tasks are entered in the reentered task area of the NEXT page, i.e., the page that you'll work on right after you leave the current one. If that area is full, put the task wherever you like, except that you never write on the current page unless it is also the last page. If you can't find a space, add it as a new task instead.
Experience
The flow of Autofocus Advance is clearly different from Autofocus 1. It is easier to cycle through the list. Your ongoing projects can advance through the list along with you. They don't cluster at the end. Instead of keeping you attached to the end of the list, they help you advance to the next page.
At the same time key properties of Autofocus 1 are preserved. There still is the intuitive selection process focusing on a single page at a time. There is now an open area on most pages, yet pages (other than the last one) still behave as closed lists while being actively worked on.
Future Work
The relative sizes of the two areas may be able to fine-tune properties of the system. So far I've always used an equal 50/50 split.
Anticipated FAQ
Q: Isn't this more like SuperFocus than Autofocus?
A: It takes a bit of geekery to see why, but it is actually important in Autofocus Advance that you don't reenter a task back on the current page. The defining twist of SuperFocus is that you can do just that! So the two systems are mutually exclusive twists on the common Autfocus theme.
Q: May I enter a really urgent task on the current page?
A: A rule tweak that would occasionally allow urgent new tasks (not reentered tasks) onto the current page is possible--in theory--without breaking the system. So far I haven't used such a tweak.
Rules
Each AF page is divided into two areas (such as by a dividing line about half way down the page, using two columns, or using facing pages.) The first is the new task area, the second is the reentered task area.
Rules for cycling through the pages, task selection, and dismissal are as in Autofocus 1. The two areas are treated as if they formed a single, contiguous page. Free space in the reentered task area doesn't keep from finishing or dismissing pages.
New tasks are entered in the new task area on the last page of the list. A new page is started when the last page's new task area is full.
Reentered tasks are entered in the reentered task area of the NEXT page, i.e., the page that you'll work on right after you leave the current one. If that area is full, put the task wherever you like, except that you never write on the current page unless it is also the last page. If you can't find a space, add it as a new task instead.
Experience
The flow of Autofocus Advance is clearly different from Autofocus 1. It is easier to cycle through the list. Your ongoing projects can advance through the list along with you. They don't cluster at the end. Instead of keeping you attached to the end of the list, they help you advance to the next page.
At the same time key properties of Autofocus 1 are preserved. There still is the intuitive selection process focusing on a single page at a time. There is now an open area on most pages, yet pages (other than the last one) still behave as closed lists while being actively worked on.
Future Work
The relative sizes of the two areas may be able to fine-tune properties of the system. So far I've always used an equal 50/50 split.
Anticipated FAQ
Q: Isn't this more like SuperFocus than Autofocus?
A: It takes a bit of geekery to see why, but it is actually important in Autofocus Advance that you don't reenter a task back on the current page. The defining twist of SuperFocus is that you can do just that! So the two systems are mutually exclusive twists on the common Autfocus theme.
Q: May I enter a really urgent task on the current page?
A: A rule tweak that would occasionally allow urgent new tasks (not reentered tasks) onto the current page is possible--in theory--without breaking the system. So far I haven't used such a tweak.
Reply by Mark Forster
Marcus:
Well done! Writing re-entered tasks in Column 2 of the next page is one of the new rules included in SuperFocus v. 3. And you're right - it does make stuff progress better.
Well done! Writing re-entered tasks in Column 2 of the next page is one of the new rules included in SuperFocus v. 3. And you're right - it does make stuff progress better.
Reply by Don R
My first thought is if you have 5 pages you're going to potentially work on one project 4 times before you finally reach the newest items on the last page. What effect does that have in practice?
Reply by Don R
To revise and extend my previous post, if you did end up working on all four pages you'd be getting a lot of stuff done besides the project(s) from the first page. In the meantime you would have been working often on a project so it would either get done or make steady progress. If you also allowed urgent matters in the second column you would not have to put them off to the last page. Call it SuperFocus Advance. :) Oh I guess you did mention that possible tweak in the last question, about possibly entering urgent items on the current page. I think it might also be treated by the "common sense" rule: if something is urgent, just do it!
Reply by Marcus
Mark: Thank you!
Don: The last page has a reentered task area, too. Under extreme circumstances, with 5 pages, you could even work on the same project for 8 consecutive page turns, or 15. But you would have done the AF selection procedure on each page. Since you trust your intuition to do a good ranking of the tasks on each page, the conclusion from ever having done a thing like this would be that your intuition found this project really more worthy of working on than every other thing on the list--much more so than you yourself suspected when you stopped working on it over and over again:-)
Don: The last page has a reentered task area, too. Under extreme circumstances, with 5 pages, you could even work on the same project for 8 consecutive page turns, or 15. But you would have done the AF selection procedure on each page. Since you trust your intuition to do a good ranking of the tasks on each page, the conclusion from ever having done a thing like this would be that your intuition found this project really more worthy of working on than every other thing on the list--much more so than you yourself suspected when you stopped working on it over and over again:-)
Reply by smileypete
How about entering urgent tasks on the *next* page (if not urgent enough to do right now with the 'common sense rule' ;-) )
Also how about entering some tasks *beyond* the last page?
Reply by Mark Forster
smileypete:
<< How about entering urgent tasks on the *next* page >>
I tried this as part of the development of SuperFocus v. 3 and it doesn't work!
<< How about entering urgent tasks on the *next* page >>
I tried this as part of the development of SuperFocus v. 3 and it doesn't work!
Reply by Tijl Kindt
Interesting concept, Marcus! Made even more so by Mark's acknowledgement that it shares rules with SFv3.
No distinction is being made between recurring and unfinished tasks, right? All are re-entered in the 2nd column of the next page?
No distinction is being made between recurring and unfinished tasks, right? All are re-entered in the 2nd column of the next page?
Reply by David Drake
Markus, this is excellent! And it sounds as if there are some very good similarities to Mark's SF3. This is a modification that I am going to implement and try! It will be intriguing to see how similar indeed your system is to the pending SuperFocus 3. :)
-David
-David
Reply by Marcus
I eliminated the two areas. The resulting ruleset is even simpler and items are always contiguous on a page. The balance between new tasks and reentered tasks on a page is slightly shifted. I compensated by including the urgent task tweak into the ruleset. If you feel that the balance is off (whether using the original ruleset or this one), you can experiment by slightly shifting the barrier position on new pages.
The Rules
Arrange for each page to have a visible barrier about halfway into the page. You could draw a line, or use the natural jump between two columns or facing pages.
Rules for cycling through the pages, task selection, and dismissal are as in AF1. Free space behind the barrier doesn't keep from finishing or dismissing pages.
New tasks are normally entered on the youngest page of the list. If the new entry would go behind the barrier, a new page is started instead. Exceptionally urgent tasks may be entered on the current page.
Reentered tasks are entered on the NEXT page, i.e., the page that you'll work on right after you leave the current one. If that page is full, put the task on any other page you like, except for the current page. If you can't find such a place, add it as a non-urgent new task.
The Rules
Arrange for each page to have a visible barrier about halfway into the page. You could draw a line, or use the natural jump between two columns or facing pages.
Rules for cycling through the pages, task selection, and dismissal are as in AF1. Free space behind the barrier doesn't keep from finishing or dismissing pages.
New tasks are normally entered on the youngest page of the list. If the new entry would go behind the barrier, a new page is started instead. Exceptionally urgent tasks may be entered on the current page.
Reentered tasks are entered on the NEXT page, i.e., the page that you'll work on right after you leave the current one. If that page is full, put the task on any other page you like, except for the current page. If you can't find such a place, add it as a non-urgent new task.
Reply by JD
Marcus - thank you for sharing this gem. Would recurring tasks have the same treatment in your opinion ie entered on the 2nd column of the next page? This would ensure they are touched on frequently so that one is on top of regular tasks.
Reply by wairererose
This is a system that I think will flow well for me - I'm going to give it a try starting tomorrow. Adding to the end of my current list right now so I can get to it first.
Reply by Tijl Kindt
Regarding unfinished tasks vs. recurring tasks:
IF you re-enter recurring tasks on the next page and a) you only (need to) do these recurring tasks once a week and b) you add about half a page of new tasks every day, THEN...
... eventually your recurring tasks will cluster at the beginning, holding up the dismissal process of those pages. You can see this by realizing that you are adding one page every two days, whereas those weekly recurring tasks are only moving forward one page every week.
Thus, I think I can pretty much conclude that you should only re-enter on the next page 1) unfinished tasks and 2) daily tasks, while you re-enter less frequently recurring tasks at the end. The re-enter on the next page rule encourages tasks to be worked on every day or two days (assuming you add a new page of tasks every day or two days), since dismissal looms over them if you don't.
@Marcus: can you comment on this? Since you have actually *used* the system, whereas I'm just hypothesizing :).
IF you re-enter recurring tasks on the next page and a) you only (need to) do these recurring tasks once a week and b) you add about half a page of new tasks every day, THEN...
... eventually your recurring tasks will cluster at the beginning, holding up the dismissal process of those pages. You can see this by realizing that you are adding one page every two days, whereas those weekly recurring tasks are only moving forward one page every week.
Thus, I think I can pretty much conclude that you should only re-enter on the next page 1) unfinished tasks and 2) daily tasks, while you re-enter less frequently recurring tasks at the end. The re-enter on the next page rule encourages tasks to be worked on every day or two days (assuming you add a new page of tasks every day or two days), since dismissal looms over them if you don't.
@Marcus: can you comment on this? Since you have actually *used* the system, whereas I'm just hypothesizing :).
Reply by Alan Baljeu
Surely the *only* reason to consider the next page is so you can get back to the task real soon. This only applies to things you started but didn't finish.
Reply by Marcus
I don't use my AF system as either a clock, timer or calendar. I'd find it unreliable as a timer or clock and clumsy as a calendar.
I feed the system with new tasks sourcing from the calendar and from weekly/monthly checklists. That covers recurring tasks that run weekly or more infrequently. What few daily recurring tasks I have, I run off a small morning checklist. They only go into the system if I don't do them right away, which isn't often.
Over time I've found that wherever I keep track of the current day's scheduled timeline (maybe a calendar page, maybe a scrap of paper) is a good place to keep track of urgent same-day tasks. That's because urgency usually implies deadlines and time commitments.
Items on my AF list therefore tend have two properties related to time: They are ready to be worked on now but don't have a deadline today. It's not an iron rule, but is usually true.
Again, all of this is because --personally-- I don't think of the Autofocus systems as timing devices.
That leaves some kinds recurring tasks that may alternatively be viewed as neverending tasks/projects, such as answering your e-mail. Yes, I treat these like other re-entered tasks, i.e., put them on the next page.
I feed the system with new tasks sourcing from the calendar and from weekly/monthly checklists. That covers recurring tasks that run weekly or more infrequently. What few daily recurring tasks I have, I run off a small morning checklist. They only go into the system if I don't do them right away, which isn't often.
Over time I've found that wherever I keep track of the current day's scheduled timeline (maybe a calendar page, maybe a scrap of paper) is a good place to keep track of urgent same-day tasks. That's because urgency usually implies deadlines and time commitments.
Items on my AF list therefore tend have two properties related to time: They are ready to be worked on now but don't have a deadline today. It's not an iron rule, but is usually true.
Again, all of this is because --personally-- I don't think of the Autofocus systems as timing devices.
That leaves some kinds recurring tasks that may alternatively be viewed as neverending tasks/projects, such as answering your e-mail. Yes, I treat these like other re-entered tasks, i.e., put them on the next page.
Reply by Mark Forster
As Marcus's new system bears a lot of resemblance to SuperFocus v. 3 which I've been testing, I think I am going to bring the testing to an end and publish the amendment now, rather than wait until I finish "War and Peace" - which was the original plan.
So just as soon as I can write the instructions I will publish them on my blog.
So just as soon as I can write the instructions I will publish them on my blog.
Reply by Seraphim
Oh great, now I'll be anxiously hitting "reload" on your blog page all morning. LOL :-)
Reply by Mark Forster
The new rules are now up on the blog.
Reply by Seraphim
Wow, that was fast!!!
Reply by Tijl Kindt
@Alan: Ok, I have to give it to you; that actually sounds pretty logical. In my defense Marcus' original rules did not distinguish recurring from unfinished tasks since they can both be seen as being 're-entered' ;).
Thanks for posting the new rules, Mark!
Thanks for posting the new rules, Mark!
Reply by Marcus
Mark, very interesting new system!
I spent some time yesterday digesting it. I now regret not having used the alternative formulation ("barrier" instead of "areas") already when I first posted Autofocus Advance.
Apart from the fact that I just like the second way better, I suspect the first wording may have also made you think of Autofocus Advance as more similar to SFv3 than it may turn out to be.
AF Advance is original Autofocus with a ruleset tweak designed to reduce resistance within the system. It is not a move away or beyond autofocus.
SFv3 is more than a tweak of AF1; it is essentially a sandwich of two parallel systems. You run a (surprisingly un-tweaked) AF 1 in the first column of each page. You use space in the second columns to run a second and much simpler system --let's call it Column 2 System, C2S. You run the systems in lockstep. AF1 feeds tasks into C2S. C2S gates progress in AF1. You could actually pull C2S out of your notebook, put it on a whiteboard, and get a mostly equivalent composite system.
The important difference regarding those similar looking rules is that in AF Advance, they tweak AF1. In SFv3, these rules do not live in the AF1 part of the sandwich, but are part of the way the C2S operates in the second columns. This makes me suspect the similarity will turn out to be somewhat smaller than the similarity in wording lead us to expect at first.
I spent some time yesterday digesting it. I now regret not having used the alternative formulation ("barrier" instead of "areas") already when I first posted Autofocus Advance.
Apart from the fact that I just like the second way better, I suspect the first wording may have also made you think of Autofocus Advance as more similar to SFv3 than it may turn out to be.
AF Advance is original Autofocus with a ruleset tweak designed to reduce resistance within the system. It is not a move away or beyond autofocus.
SFv3 is more than a tweak of AF1; it is essentially a sandwich of two parallel systems. You run a (surprisingly un-tweaked) AF 1 in the first column of each page. You use space in the second columns to run a second and much simpler system --let's call it Column 2 System, C2S. You run the systems in lockstep. AF1 feeds tasks into C2S. C2S gates progress in AF1. You could actually pull C2S out of your notebook, put it on a whiteboard, and get a mostly equivalent composite system.
The important difference regarding those similar looking rules is that in AF Advance, they tweak AF1. In SFv3, these rules do not live in the AF1 part of the sandwich, but are part of the way the C2S operates in the second columns. This makes me suspect the similarity will turn out to be somewhat smaller than the similarity in wording lead us to expect at first.
Reply by Mark Forster
Marcus:
I'm not sure I entirely follow what you are saying here, especially the bit about my column 2 being a mostly equivalent composite system.
As far as I can see the only differences in the ordinary working of your system and my system are:
- You re-enter all tasks on the next page, while I re-enter only unfinished tasks on the next page.
- You do not have to clear all tasks in column 2 before moving on, while I do have to clear them.
There are other differences in detail, especially in the rules for dismissal, but they are incidental.
My main worry with your system is that I usually have considerably more recurring tasks than new tasks, and I'm not sure how that would work out in practice. Even if one adjusted the position of the barrier to allow for this, wouldn't it just result in new stuff hanging around for much longer before being actioned?
I'm not sure I entirely follow what you are saying here, especially the bit about my column 2 being a mostly equivalent composite system.
As far as I can see the only differences in the ordinary working of your system and my system are:
- You re-enter all tasks on the next page, while I re-enter only unfinished tasks on the next page.
- You do not have to clear all tasks in column 2 before moving on, while I do have to clear them.
There are other differences in detail, especially in the rules for dismissal, but they are incidental.
My main worry with your system is that I usually have considerably more recurring tasks than new tasks, and I'm not sure how that would work out in practice. Even if one adjusted the position of the barrier to allow for this, wouldn't it just result in new stuff hanging around for much longer before being actioned?
Reply by Marcus
Mark: It helped me understand SFv3 (which is new to me) to re-frame it as a "composite system" built out of one part original AF1 (which I know) and one part dynamic round robin scheduler (which I know) working in lockstep with the first feeding tasks into the second.
Since --in this re-framing-- the re-entry rule operates within the second part, which is quite unlike AF1, I concluded that from the very similar wording we need not expect very similar behaviour.
Regarding new stuff hanging around longer: yes, compared to me very much clinging to the end of the list in AF1, I tend to spend more time "away" on other pages. It works for me because "do it tomorrow" usually works for me. And I'm not kept away from the last page for days, just hours sometimes.
Since --in this re-framing-- the re-entry rule operates within the second part, which is quite unlike AF1, I concluded that from the very similar wording we need not expect very similar behaviour.
Regarding new stuff hanging around longer: yes, compared to me very much clinging to the end of the list in AF1, I tend to spend more time "away" on other pages. It works for me because "do it tomorrow" usually works for me. And I'm not kept away from the last page for days, just hours sometimes.